|
|
|
|
|
|
|
Figure 6.9.
The use-case diagram for the use case Deposit Funds into Basic Personal
Checking Account. |
|
|
|
|
|
|
|
|
Recall that a use case is implemented in one or more scenarios. Each scenario represents an instance of the use case, given a set of conditions and assumptions. A scenario is realized in the form of a sequence diagram or scenario script. Remember, a set of scenarios for a use case typically consists of a normal path accompanied by one or more abnormal paths. |
|
|
|
|
|
|
|
|
In much the same way, a well-written test script is the realization of a test case, given a set of conditions and assumptions. Thus, a test script is equivalent to a use-case scenario and can be realized in the form of a sequence diagram or scenario script as well. Figure 6.10 illustrates the sequence diagram for the normal path of your sole use case. |
|
|
|
|
|
|
|
|
Figure 6.10.
The sequence diagram for the use case Deposit Funds into Basic Personal
Checking Account. |
|
|
|
|
|
|
|
|
For the abnormal paths of a use case, you can use either a sequence diagram or a scenario script for each path. An abnormal path is equivalent to an exception. That is, an abnormal path is any deviation from the normal path of a use case. Most abnormalities are not complex, so a scenario script would be sufficient. For your example, you will create a scenario script to document the scenario in which the account number on the deposit is wrong: |
|
|
|
|
|
